Skip to content

chore: prepare AutoParts for public portfolio release#8

Open
tomiloki wants to merge 1 commit into
mainfrom
codex/github-readiness
Open

chore: prepare AutoParts for public portfolio release#8
tomiloki wants to merge 1 commit into
mainfrom
codex/github-readiness

Conversation

@tomiloki
Copy link
Copy Markdown
Owner

@tomiloki tomiloki commented May 8, 2026

Closes #1
Closes #2
Closes #3
Closes #4
Closes #5
Closes #6
Closes #7

Pull Request Checklist

Objetivo

  • Preparar AutoParts para publicacion como portfolio profesional: presentacion publica, seguridad runtime, hardening API, tests, CI/e2e y refactor minimo del backoffice.

Alcance

  • El cambio esta acotado a GitHub readiness y no mezcla nuevas funcionalidades de negocio.
  • Afecta catalogo publico, respuesta Webpay commit, CI, docs, assets publicos y estructura del dashboard admin.

Calidad

  • Backend: python manage.py makemigrations --check --dry-run, python manage.py check y python manage.py test ejecutados.
  • Frontend: npm run lint, npm run test:ci -- --passWithNoTests y npm audit --omit=dev --audit-level=moderate ejecutados.
  • No se ejecuto npm run build localmente por regla del repo; queda para GitHub Actions.
  • No se subieron secretos ni artefactos temporales.

Evidencia

  • Backend: 19 tests OK.
  • Frontend: 6 tests OK.
  • Runtime audit: 0 vulnerabilities.
  • CI actualizado para correr Playwright e2e contra Docker smoke.

Riesgos y rollback

  • Riesgo: react-router-dom actualizado requiere mappers Jest por compatibilidad con CRA/Jest 27.
  • Riesgo: Webpay commit ahora devuelve payload minimo; frontend consulta detalle de orden autenticado cuando esta disponible.
  • Rollback: revertir el commit chore: prepare AutoParts for public portfolio release.

@tomiloki tomiloki added the type:chore Maintenance/tooling PR label May 8, 2026
@gitguardian
Copy link
Copy Markdown

gitguardian Bot commented May 8, 2026 •
edited
Loading

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@tomiloki tomiloki force-pushed the codex/github-readiness branch from 7c21fc3 to 9777c2c Compare May 8, 2026 20:10
@tomiloki tomiloki force-pushed the codex/github-readiness branch from 9777c2c to eaec617 Compare May 8, 2026 20:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment